System and method for measuring data network quality

ABSTRACT

The invention relates to a system and a method for measuring the quality of a data network. More specifically, the invention relates to a system and a method for measuring the quality of a data network using a client computer and a server computer communicating using a connection-less transmission protocol.

CLAIM TO PRIORITY

[0001] This application claims the benefit of our co-pending U.S. provisional patent application entitled “METHOD AND SYSTEM TO MEASURE PACKET SWITCHED NETWORK QUALITY” filed Apr. 16, 2003 and assigned Ser. No. 60/463,455, which is incorporated by reference herein.

[0002] BACKGROUND OF THE DISCLOSURE

[0003] 1. Field of the Invention

[0004] The invention relates to a system and a method for measuring the quality of a data network. More specifically, the invention relates to a system and a method for measuring the quality of a data network using a client computer and a server computer communicating using a connection-less transmission protocol.

[0005] 2. Description of the Prior Art

[0006] A method to measure data networks is known from Iperf (http://dast.nlanr.net/Projects/Iperf). Iperf uses TCP and UDP to measure the performance of an IP network. With UDP Iperf is able to measure packet loss and delay jitter.

[0007] Another method to measure data networks is known from rfc792. Rfc792 describes the Internet Control Message Protocol (ICMP). With ICMP it is possible to send measurement data packets between two computers. A first computer sends an ICMP packet containing an originate timestamp to a second computer. The second computer adds a receive timestamp to the ICMP packet when it receives the packet and adds a transmit timestamp to the ICMP packet when it sends the packet back to the first computer.

[0008] Aim of the Invention

[0009] The aim of the invention is to provide an alternative system and method for measuring the quality of a data network.

SUMMARY OF THE INVENTION

[0010] The present invention provides an alternative solution for measuring the quality of a data network.

[0011] According to an aspect of the invention a system is provided for measuring the quality of a data network, the system comprising a client computer and a server computer, the client computer and the server computer being arranged to communicate via the data network using a connection-less transmission protocol, e.g., UDP/IP.

[0012] The client computer can be arranged to send one or more data packets to the server computer. The client computer can comprise a client processor connected to a client memory, the client processor being arranged to read from the client memory for each data packet a client interval value, a client packet size value and a packet type value. The client memory can be a file stored on a disk, making it possible to permanently store the information. The packet type value can be a representation of “normal packet” or “burst packet”, enabling later on different network quality calculations for different type of packets. The data packets can comprise a first timestamp indicating the time of sending. The client computer can be arranged to send the data packets with a client interval time equal to the client interval value, the data packets comprising the packet type value and a client payload, the client payload filling the data packets up to a first predefined size equal to the client packet size value. The client payload can be a predefined bit pattern or a random bit pattern. Each data packet can comprise a sequence number, enabling the identification of the order of the packets.

[0013] The server computer can be arranged to receive at least one of the data packets. The server computer can comprise a server processor connected to a server memory. The server processor can be arranged to read from the server memory a timeout value indicating the predefined amount of time, a server interval value, a quantity value or a server packet size value. The server computer can further be arranged to send, for each received data packet, a modified data packet to the client computer, the modified data packet comprising the first timestamp and a second timestamp indicating the time of receiving. The modified data packet can comprise a server payload, the server payload filling the modified data packet up to a second predefined size equal to the server packet size value. This enables measuring asymmetric network load where uplink and downlink have different packet sizes. The server payload can be a predefined bit pattern or a random bit pattern. The server computer can be arranged to send one or more timeout data packets to the client computer when a predefined amount of time lapsed since receiving the last data packet in the server computer. This is advantageous because it increases the detectability of lost packets. The server computer can be arranged to send the timeout data packets with a server interval time equal to the server interval value, until a next data packet is received. The maximum number of timeout data packets send can be equal to the quantity value. This enables a controlled detection of lost packets.

[0014] The client computer can be arranged to send a configuration packet to the server. The configuration packet can comprise the timeout value, the server interval value, the quantity value and/or the server packet size value. This can be advantageous because the same client computer using the same connection-less transmission protocol can be used. For configuration the client computer can be arranged to communicate with the server computer via the data network using a connection-oriented transmission protocol, e.g., TCP/IP. This can be advantageous when it has to be guaranteed that the server computer receives configuration data correctly. The server computer is arranged to receive the configuration packet. The server processor can be arranged to write to the server memory the timeout value, the server interval value, the quantity value and/or the server packet size value, so it becomes available for usage immediately.

[0015] The client computer can be arranged to store a logfile. The logfile can comprise all modified data packets received from the server computer. The logfile can further comprise all timeout data packets received from the server computer. All modified data packets received from the server computer can be stored in a first logfile. All timeout data packets received from the server computer can be stored in a second logfile. Each data packet can be stored in a ring buffer. The client computer can be arranged to check each modified data packet received from the server with the contents of the ring buffer. The client computer can be arranged to delete the data packet from the ring buffer if the corresponding modified data packet is not received within the length of the ring buffer, and in this case store the data packet in the second logfile.

[0016] The client computer can arranged to calculate a round-trip-time by subtracting the first timestamp from a timestamp indicating when the modified data packet is received in the client computer. The client computer can be arranged to store the round-trip-time in the first logfile, enabling later usage of the data.

[0017] The client computer can be arranged to calculate a client-to-server-latency by subtracting the second timestamp from the first timestamp. The client computer can be arranged to store the client-to-server-latency in the first logfile, enabling later usage if the data.

[0018] The client computer can be arranged to read from the first logfile the packet type value, the client-to-server-latency and the round-trip-time. The client computer can be arranged to calculate for each modified data packet with the packet type value equal to the representation of “normal packet” a server-to-client-latency by subtracting the client-to-server-latency from the round-trip-time.

[0019] The client computer can be arranged to read from the first logfile the packet type value. The client computer can be arranged to calculate a downlink bandwidth using:

(#BytesPerPacket+Overhead)*(#BurstPackets)/(t2−t1)

[0020] where #BytesPerPacket equals the length of the modified data packet in bytes; Overhead equals the length of protocol header overhead in bytes; #BurstPackets equals the number of modified data packets stored in the first logfile with the packet type value equal to the representation of “burst packet”; t1 equals a timestamp indicating when the first modified data packet is received in the client computer; t2 equals a timestamp indicating when the last modified data packet is received in the client computer.

[0021] The client computer can be arranged to read from the first logfile the packet type value. The client computer can be arranged to calculate an uplink bandwidth using:

(#BytesPerClientPacket+Overhead)*(#BurstPackets)/((t2+t4)−(t1+t3))

[0022] where #BytesPerClientPacket equals the length of the data packet in bytes; Overhead equals the length of protocol header overhead in bytes; #BurstPackets equals the number of modified data packets stored in the first logfile with the packet type value equal to the representation of “burst packet”; t1 equals a timestamp indicating when the first modified data packet is received in the client computer; t2 equals a timestamp indicating when the last modified data packet is received in the client computer; t3 equals the client-to-server-latency of the first modified data packet; t4 equals the client-to-server-latency of the last modified data packet.

[0023] The client computer can be arranged to read from the first logfile the round-trip-time and the sequence number. The client computer can be arranged to calculate a roundtrip outage using:

if(Rtt2−Rtt1)>t5 then roundtrip outage=true

[0024] where Rtt2 equals the round-trip-time; Rtt1 equals the round-trip-time of the previous modified data packet, the client computer being arranged to identify the previous modified data packet by the sequence number; t5 equals a predefined amount of time.

[0025] The client computer can be arranged to read from the first logfile the client-to-server-latency and the sequence number. The client computer can be arranged to calculate a downlink outage using:

if(Rtt4−Rtt3)>t5 then downlink outage=true

[0026] where Rtt4 equals the client-to-server-latency; Rtt3 equals the client-to-server-latency of the previous modified data packet, the client computer being arranged to identify the previous modified data packet by the sequence number; t5 equals a predefined amount of time.

[0027] The client computer can be arranged to read from the first logfile the sequence number. The client computer can be arranged to calculate an uplink outage using:

if(Rtt6−Rtt5)>t5 then uplink outage=true

[0028] where Rtt6 equals the server-to-client-latency; Rtt5 equals the server-to-client-latency of the previous modified data packet, the client computer being arranged to identify the previous modified data packet by the sequence number; t5 equals a predefined amount of time.

[0029] The client computer can be arranged to determine a number of lost packets between two modified data packets, by analyzing the sequence numbers. This enable a good overview of packet loss.

[0030] The client computer can be arranged to combine the calculated values with low-level measurement data from a mobile telephone and/or geographic information data. This is advantageous when poor data network quality is to be indicated in geographical areas, simplifying a search for weak spots in the data network.

[0031] According to an aspect of the invention a method is provided for measuring the quality of a data network in a system comprising a client computer and a server computer, the client computer and the server computer being arranged to communicate via the data network using a connection-less transmission protocol. The method can comprise one or more of the steps of sending one or more data packets from the client computer to the server computer, the data packets comprising a first timestamp indicating the time of sending, receiving at least one of the data packets in the server computer, sending, for each received data packet, a modified data packet from the server computer to the client computer, the modified data packet comprising the first timestamp and a second timestamp indicating the time of receiving, sending one or more timeout data packets from the server computer to the client computer when a predefined amount of time lapsed since receiving the last data packet in the server computer, reading from a server memory in the server computer a timeout value indicating the predefined amount of time, a server interval value and a quantity value, sending the timeout data packets with a server interval time equal to the server interval value, until a next data packet is received, and the maximum number of timeout data packets equals the quantity value, reading from a client memory in the client computer for each data packet a client interval value, a client packet size value and a packet type value, sending the data packets with a client interval time equal to the client interval value, the data packets comprising the packet type value and a client payload, the client payload filling the data packets up to a first predefined size equal to the client packet size value.

BRIEF DESCRIPTION OF THE DRAWINGS

[0032] The invention will be explained in greater detail by reference to exemplary embodiments shown in the drawings, in which:

[0033]FIG. 1 shows an architectural overview of the system;

[0034]FIG. 2 shows a data packet or a modified data packet and its elements;

[0035]FIG. 3 shows a control packet and its elements;

[0036]FIG. 4 shows a time sequence diagram of packets sent between a client computer and a server computer.

DETAILED DESCRIPTION OF THE INVENTION

[0037] For the purpose of teaching of the invention, preferred embodiments of the method and system of the invention are described in the sequel. It will be apparent to the person skilled in the art that other alternative and equivalent embodiments of the invention can be conceived and reduced to practice without departing from the true spirit of the invention, the scope of the invention being only limited by the claims as finally granted.

[0038] The measurement system consists of a client-server approach. The invention is explained for usage in a GPRS network, but can also be used in any other packet switched network, such as, among others, UMTS, LAN, WAN and Internet. As connection-less transmission protocol the UDP/IP protocol is used in the examples. Other connection-less transmission protocols could just as well have been used.

[0039] In this example the client computer is a laptop computer in a car connected via a GPRS phone to the GPRS network. Other clients can be used It sends a defined pattern of UDP packets to the server computer. The server responses to each data packet with another packet (a modified data packet).

[0040] UDP is a OSI level 4 protocol which leaves the IP behavior as transparent as possible. Unlike TCP (the other level well known 4 protocol) UDP does not restrict transmission of packets or force retransmissions in case of missed packets. Using UDP a level 7 application can keep full contact with the IP layer.

[0041] The UDP server is located on a fixed position in the datanetwork to be tested. E.g., the server can be directly connected to an Access Point of a GGSN to avoid measurement inaccuracies. Later the server was connected to the Internet, which introduced only a few milliseconds extra delay which is neglectible with respect to the delay in the GPRS system.

[0042] The server responds to each packet with the same packet, extended with its time of arrival and possibly filled up with a predefined extra payload.

[0043] In case the server doesn't receive any UDP-packets within a certain time after reception of the last packet it starts sending a predefined number of special packets (timeout packets). Reception of these server-originated packets gives an indication to the client that the upstream stopped, and the duration of the upstream interruption.

[0044] The following server parameters can be remotely configured, using a secure TCP connection with the server on the same port:

[0045] the amount of octets to which it shall fill up the reflected UDP-packets;

[0046] the time before it starts sending its own packets to indicate the interruption of client packets;

[0047] the number of own packets after interruption of client packets.

[0048] The measurement logging is done by two logfiles: the A-logfile (second logfile) and the R-logfile (first logfile). The R-logfile is filled with all packets that returned from the server. The content of the A-file consists of general information on the measurement, like the used packet pattern, as well as exceptions, which have been recorded by the client, like lossed packets.

[0049] The client stores every sent packet in a ringbuffer, and checks every received packet which the contents of the ringbuffer. If the packet is recognized, it is stored in the R-result file, together with its round trip time and the one-way delay time. The latter is only usable if client and server clocks are synchronized.

[0050] In case the packet is unknown the packet content is stored in the A-log file. This happens for example in case of reception of a server originated packet.

[0051] If a packet did not return within the length of the ringbuffer, it is deleted from the buffer and stored in the A-logfile as ‘lost’. Packets which are not marked as ‘returned’ when the measurement stops are also stored in the A-logfile.

[0052] Server Part

[0053] The server listens on a defined port for both UDP packets and TCP connect requests. The port number is given as a parameter in the command line to boot the server.

[0054] In case of reception of a UDP packet:

[0055] If the first character of the client packet is a ‘C’ (i.e., this is a control data packet) and the characters from the 19th until the 30th position are valid numbers the packet is processed as follows:

[0056] Syntax of the command packet: CYYYYMMDDHHmmSSNNNiiiiggggnnn

[0057] Example: C20030422105256873012507000050

[0058] Where:

[0059] YYYY: year, 2003

[0060] MM: month, 04

[0061] DD: day, 22

[0062] HH: hour, 10

[0063] mm: minute, 52

[0064] SS: second, 56

[0065] NNN: millisecond, 873

[0066] iiii: interval between the packets, 125 ms

[0067] gggg: packet size, 700 octets

[0068] nnn: number of packets, 50

[0069] The date and time stamp of the packet reflect its actual transmission time, derived from the client's clock. After reception of this packet the server starts the server-originated packet sequence according to the parameters iiii, gggg and nnn. After sending the last packet the server returns to standby state. The payload of the packets sent by the server contains the RTT's of the last measurement session.

[0070] The server remains alert for other commands during the transmission. These commands might override former commands. Example: if the server is in the state of transmitting 1000 packets with an interval of 1000 ms, the client may send a new command requesting 1 packet. Then only this single packet will be sent by the server and the other packets will not be sent.

[0071] If the received UDP packet does not start with the character ‘C’ the packet is sent back to the client, extended with a timestamp which indicates the time on which the server received the packet. It is coded in the same way: YYYYMMDDHHmmSSNNN.

[0072] In case the packet size is less than the requested size the packet is filled up to the requested size, using a sequence of the character ‘A’ (predefined bit pattern).

[0073] After reception of a packet like this, a timer is started. This timer can be remotely configured using the HW command (see the TCP section below). If no new packet is received before the timer expires the server starts sending server-originated packets with a packet size, to be configured with the HE command. The packets are coded like:

[0074] SqqqqYYYYMMDDHHmmssNNN, where:

[0075] ‘S’: ‘server originated packet’;

[0076] qqqq: packet sequence number;

[0077] YYYYMMDDHHmmssNNN: date and time stamp of packet transmission.

[0078] The packet sequence numbers count from the maximum (configured by the HE command, default 19) down to zero.

[0079] Treatment of TCP

[0080] TCP is used in a Telnet-like session to configure the server remotely to obtain maximum flexibility. In case of a TCP connect event the server sends the string ‘password:’ to the client. If the next received string via the TCP connection does not match the defined password the server terminates the TCP connection. If the next received string matches the defined password the server leaves the TCP connection open and sends an overview of the commands to the user. These commands are:

[0081] HV<n>: all returned UDP packets are filled up to <n> octets (if <n> < packet size to be returned, then we do not fill the packet up, nor cut it down to prevent loss of information)

[0082] HW<n>: if within <n> milliseconds no UDP packets are received, the server starts transmitting its own packets;

[0083] HI<n> <n> defines the time in milliseconds between the server originated packets;

[0084] HE<n> <n> defines the maximum number of server originated packets.

[0085] Each command must be given as a separate line.

[0086] The default settings are: HV0, HW1000, HI1000, HE20.

[0087] The set parameters are stored in memory. These could be stored in a configuration file, which loads the last parameters on reboot.

[0088] On TCP disconnect the server terminates the session and a new login is required.

[0089] Client Part

[0090] A user interface can offer the user three main ways to generate UDP packets:

[0091] 1. With a defined time interval (uniform);

[0092] 2. With a defined time interval, poisson distributed;

[0093] 3. According to a packet transmission schedule file (Chirp).

[0094] In all cases the transmitted packet size and packet interval time can be defined. In the first two cases the packet size and interval time definition are fixed during the whole test. In the case using the packet transmission schedule file each transmitted packet can have a different packet size and interval time, to be defined in an external file stored on disk: ‘CHIRP.TXT’. An example of this file: 2000 300 H 700 300 H 700 300 H 700 300 H 700 300 H 700 300 H 700 300 H 700 300 H 10 30 B 10 30 B 10 30 B

[0095] Each row of this file describes one packet.

[0096] The first column defines the waiting time before the packet is sent, the second column defines the packet size in octets and the last column defines the first letter of the packet to be sent. Fields are delimited with a space.

[0097] Analysis of ‘Chirp mode’ packet sequences requires the packets to be identified. In the actual version the analysis program identifies slow streaming packets with the letter ‘H’ (normal packets) and buffer filling stream packets with the letter ‘B’ (burst packets).

[0098] The client stores every sent packet in a ring buffer slot, and marks it as ‘sent’. If this ringbuffer slot is still filled with a frame which did not return so far, this frame is deleted from the ringbuffer and marked as lost in the A-logfile.

[0099] All packets are reflected by the server, which appends a timestamp and (depending on its configuration) additional payload.

[0100] At the start of each test, two logfiles are opened by the client: ‘AYYYYMMDDHHmmSS.TXT’ and ‘RYYYYMMDDHHmmSS.TXT’ in which YYYYMMDDHHmmSS reflects the date and time of the start of the measurement.

[0101] The A-file contains general information on the measurement, like the content of the chirp file, the size of the received packets from the server, and exceptions which occurred, like lost packets and reception of unidentified packets.

[0102] The R-file contains the reception time, roundtriptime, one way delay time and the header letter of each matched packet.

[0103] The client is continually alert on incoming UDP packets. Each received packet is compared with the content of the ringbuffer. If the packet matches, the client clears its copy in the ringbuffer so the ringbuffer slot becomes free. The client calculates the roundtrip time of the packet. If server and client are synchronized the one way delay can be calculated also, taking the server time stamp into account. The results are stored in the R-file.

[0104] If a frame does not match with the content of the ringbuffer it is stored in the A-log file as unidentified.

[0105] Measurement Procedure

[0106] The UDP network test consists of one or more testsequences.

[0107] A sequence of frames is transmitted by a UDP client over the GPRS network under test according to the content of a so called ‘chirpfile’. These frames are received by a UDP server, tagged with the reception time, extended to a defined number of octets (e.g., 700 octets), and sent back to the client.

[0108] Our chirpfile now consists. of the following settings (to be read in one column) 700 300 H 700 300 H 700 300 H 700 300 H 700 300 H 700 300 H 700 300 H 700 300 H 700 300 H 700 300 H 700 300 H 700 300 H 700 300 H 10 30 B 10 30 B 10 30 B 10 30 B 10 30 B 10 30 B 10 30 B 10 30 B 10 30 B 10 30 B 10 30 B 10 30 B 10 30 B 10 30 B 10 30 B 10 30 B 6000 30 B 700 300 H 700 300 H 700 300 H 700 300 H 700 300 H 700 300 H 700 300 H 700 300 H 700 300 H 700 300 H 700 300 H 700 300 H 700 300 H 10 400 U 10 400 U 10 400 U 10 400 U 10 400 U 10 400 U 10 400 U 10 400 U 10 400 U 10 400 U 10 400 U 10 400 U 10 400 U 10 400 U 10 400 U 6000 400 U

[0109] This file is treated as follows:

[0110] At start of the measurement 13 frames of 300 octets are sent with an interval time of 700 ms. All these frames are labeled with the letter ‘H’ to indicate that they are primary used to measure network latency. The server expands these frames to 700 octets and sends them back to the client.

[0111] This frame sequence is then followed by 17 frames of 30 octets, sent with an interval time of 10 ms. The frames within this burst are labeled with the letter ‘B’ to indicate their use for a downlink bandwidth measurement. The server expands these frames to 700 octets and returns them through the downlink.

[0112] After this burst a is sent, 6000 ms pause follows. This time is used to let the network buffers empty themselves from the downlink bandwidth measurement burst.

[0113] After this a new frame sequence of 12 frames of 300 octets is sent, each frame with an interval time of 700 ms, to do a second network latency test. All these frames are returned by the server filled up to 700 octets.

[0114] Finally a burst of 16 frames of 400 octets are sent with an interval time of 10 ms. With this burst uplink buffers are filled, to measure the available uplink bandwidth. The server also expands these frames to 700 octets and sends them back. A 6000 ms pause concludes the sequence. During this time the network may empty its buffers and prepare itself for the next test sequence.

[0115] The sequence is continuously repeated until the operator stops it.

[0116] If the server does not receive client frames anymore during a period of more than one second after reception of the last frame, it starts sending 20 server-originated frames with an interval of 500 ms towards the client's IP-address and port. This process stops if new frames are received from the client.

[0117] Note: The server-originated frame process can be changed by the user. The user may change the number of frames (default 20), their interval time (default 500 ms), and the time delay after which the process starts (default 1000 ms).

[0118] Of each frame sent by the UDP client the label letter (packet type value) [L] as well as the transmit time (timestamp) [1] is included in the frame by the client. At reception the server adds its reception (=transmission) time stamp [2]. When the client receives the frame back it records its reception time [3] and calculates the roundtriptime [4] by subtracting [1] from [3] and the client to server time [5] by subtracting [1] from [2]. It stores from each file [3], [4], [5] and [L] in a log file.

[0119] Note: Client and server clocks are not (very well) synchronized. Still the server timestamp [2] can be used for several interesting calculations.

[0120] In a second log file all special events are recorded, like lost and unexpected frames. This log also contains a description of the measurement circumstances.

[0121] Post Processing Calculations

[0122] Latency measurements are used to determine quality of interactive traffic. The frames with [L]=‘H’ are used for this purpose.

[0123] RTT per frame: use [4] from the log file.

[0124] Determine the client to server latency [5] of each frame, search for its minimum value, and determine for this frame a certain time value [V] for which yields: [V]:=250 ms−[5]. [V] may be a negative value.

[0125] Next, calculate for all frames normalized client to server time [5′]:=[5]+[V].

[0126] Note: the 250 ms value is only an example. Any user-defined value may be used here. Absolute latency results are not possible in this way, but a good impression of the dynamic performance can be obtained.

[0127] Server to client latency [6] per frame: calculate for each frame [6]:=[4]−[5′].

[0128] Bandwidth measurements are used to determine downlink and uplink traffic speed.

[0129] For the downlink bandwidth calculation, the frames with [L]=‘B’ of one burst are used.

[0130] Suppose [DS] as the number of octets per frame, reflected by the server.

[0131] Downlink bandwidth:=([DS]+28 octets)*(<number of frames received from server>)/([3]last frame−[3]first frame).

[0132] Note: 28 octets are added to represent IP and UDP frame overhead. The calculations are made to determine bandwidth on IP-level. Therefore frame headers should be taken into consideration.

[0133] Note: If too few frames are received during due to frame loss a bandwidth measurement may be discarded. For purity purposes the number of lost frames during bandwidth measurement is reported.

[0134] For the uplink bandwidth calculation the frames with [L]=‘U’ of one burst are used. Now the time stamp that the server receives the client frames is taken into account.

[0135] Suppose [US] as the number of octets per frame, sent by the client in the burst.

[0136] Uplink bandwidth:=([US]+28 octets)*(<number of frames received from server>)/(([3]last frame+[5]last frame)−([3]first frame+[5]first frame))

[0137] Note: 28 octets are added to represent IP and UDP frame overhead. The calculations are made to determine bandwidth on IP-level. Therefore frame headers should be taken into consideration.

[0138] Note: If too few frames are received during due to frame loss a bandwidth measurement may be discarded. For purity purposes the number of lost frames during bandwidth measurement is reported.

[0139] An outage is the event that a link remains silent during a minimum predefined time.

[0140] Roundtrip outages (All outages, whether uplink or downlink):

[0141] if (roundtriptime [4]received frame−roundtriptime [4]former received frame)>2000 ms

[0142] then an outage is reported.

[0143] If between these two frames one or more frames were lost, this is included in the outage report.

[0144] Downlink outages:

[0145] if (latency [5′]received frame−latency [5′]former received frame)>2000 ms

[0146] then an outage is reported.

[0147] If between these two frames one or more frames were lost, this is included in the outage report.

[0148] Uplink outages:

[0149] if (latency [6]received frame−latency [6]former received frame)>2000 ms

[0150] then an outage is reported.

[0151] If between these two frames one or more frames were lost, this is included in the outage report.

[0152] Of each outage is reported:

[0153] time stamp

[0154] time duration

[0155] number of lost frames during the outage

[0156] Note: The time constant can be configured by be user (default 2000 ms).

[0157] Geographical Information

[0158] By combining the post processing calculations with simultaneously performed low level measurement by the mobile telephone (e.g., radio channel number, base station identity, mobility figures, field strength and/or radio link control) and/or geographic information (e.g., using GPS) the network quality at a geographic location becomes visible. This enables indicating poor data network quality in geographical areas, simplifying a search for weak spots in the data network. 

1. System for measuring the quality of a data network (3), the system comprising a client computer (1) and a server computer (2), the client computer (1) and the server computer (2) being arranged to communicate via the data network (3) using a connection-less transmission protocol, the client computer (1) being arranged to send one or more data packets (1001) to the server computer (2), the data packets comprising a first timestamp (103) indicating the time of sending, the server computer (2) being arranged to receive at least one of the data packets, the server computer further being arranged to send, for each received data packet, a modified data packet (1002) to the client computer (1), the modified data packet comprising the first timestamp (103) and a second timestamp (105) indicating the time of receiving, wherein the server computer (2) is arranged to send one or more timeout data packets (1003) to the client computer when a predefined amount of time lapsed (1004) since receiving the last data packet in the server computer (2).
 2. System according to claim 1, wherein the server computer (2) comprises a server processor (2 a) connected to a server memory (2 b), the server processor (2 a) being arranged to read from the server memory (2 b) a timeout value indicating the predefined amount of time, a server interval value and a quantity value, the server computer (2) being arranged to send the timeout data packets (1003) with a server interval time equal to the server interval value, until a next data packet (1001) is received, and the maximum number of timeout data packets equals the quantity value.
 3. System according to claim 2, wherein the client computer (1) comprises a client processor (1 a) connected to a client memory (1 b), the client processor (1 a) being arranged to read from the client memory (1 b) for each data packet a client interval value, a client packet size value and a packet type value, the client computer (1) being arranged to send the data packets (1001) with a client interval time equal to the client interval value, the data packets comprising the packet type value (101) and a client payload (104), the client payload (104) filling the data packets up to a first predefined size equal to the client packet size value.
 4. System according to claim 3, wherein the packet type value is a representation of “normal packets” or “burst packets”.
 5. System according to claim 3, wherein the client memory (1 b) is a file stored on a disk.
 6. System according to claim 1, wherein each data packet comprise a sequence number (102).
 7. System according to claim 1, wherein the server processor (2 a) is arranged to read from the server memory (2 b) a server packet size value, the modified data packet comprising a server payload (106), the server payload filling the modified data packet up to a second predefined size equal to the server packet size value.
 8. System according to claim 3, wherein the client payload (104) and/or the server payload (106) comprises a predefined bit pattern.
 9. System according to claim 3, wherein the client payload (104) and/or the server payload (106) comprises a random bit pattern.
 10. System according to claim 1, wherein the connection-less transmission protocol is UDP/IP.
 11. System according to claim 2, wherein the client computer (1) is arranged to send a configuration packet (1005) to the server computer (2), the configuration packet comprising the timeout value (201), the server interval value (202), the quantity value (203) and/or the server packet size value (204), the server computer (2) is arranged to receive the configuration packet, and the server processor (2 a) is arranged to write to the server memory (2 b) the timeout value, the server interval value, the quantity value and/or the server packet size value.
 12. System according to claim 2, wherein, for the purpose of configuring the server computer (2), the client computer (1) is arranged to communicate with the server computer (2) via the data network (3) using a connection-oriented transmission protocol, the server computer (2) is arranged to receive configuration data from the client computer (1), the configuration data comprising the timeout value, the server interval value, the quantity value and/or the server packet size value, and the server processor (2 a) is arranged to write to the server memory (2 b) the timeout value, the server interval value, the quantity value and/or the server packet size value.
 13. System according to claim 12, wherein the connection-oriented transmission protocol is TCP/IP.
 14. System according to claim 1, wherein the client computer (1) is arranged to store a logfile, the logfile comprising all modified data packets received from the server computer (2), the logfile further comprising all timeout data packets received from the server computer (2).
 15. System according to claim 14, wherein all modified data packets received from the server computer (2) are stored in a first logfile, and all timeout data packets received from the server computer (2) are stored in a second logfile.
 16. System according to claim 15, wherein the client computer (1) stores each data packet in a ring buffer, the client computer (1) being arranged to check each modified data packet received from the server with the contents of the ring buffer, the client computer (1) being arranged to delete the data packet from the ring buffer if the corresponding modified data packet is not received within the length of the ring buffer, and in this case store the data packet in the second logfile.
 17. System according to claim 16, wherein the client computer (1) is arranged to calculate a round-trip-time by subtracting the first timestamp from a timestamp indicating when the modified data packet is received in the client computer (1), and the client computer (1) is arranged to store the round-trip-time in the first logfile.
 18. System according to claim 16, wherein the client computer (1) is arranged to calculate a client-to-server-latency by subtracting the second timestamp from the first timestamp, and the client computer (1) is arranged to store the client-to-server-latency in the first logfile.
 19. System according to claim 18, wherein the client computer (1) is arranged to read from the first logfile the packet type value, the client-to-server-latency and the round-trip-time, and the client computer (1) is arranged to calculate for each modified data packet with the packet type value equal to the representation of “normal packet” a server-to-client-latency by subtracting the client-to-server-latency from the round-trip-time.
 20. System according to claim 18, wherein the client computer (1) is arranged to read from the first logfile the packet type value, and the client computer (1) is arranged to calculate a downlink bandwidth using: (#BytesPerPacket+Overhead)*(#BurstPackets)/(t2−t1) where #BytesPerPacket equals the length of the modified data packet in bytes; Overhead equals the length of protocol header overhead in bytes; #BurstPackets equals the number of modified data packets stored in the first logfile with the packet type value equal to the representation of “burst packet”; t1 equals a timestamp indicating when the first modified data packet is received in the client computer (1); t2 equals a timestamp indicating when the last modified data packet is received in the client computer (1).
 21. System according to claim 18, wherein the client computer (1) is arranged to read from the first logfile the packet type value, and the client computer (1) is arranged to calculate an uplink bandwidth using: (#BytesPerClientPacket+Overhead)*(#BurstPackets)/((t2+t4)−(t1+t3)) where #BytesPerClientPacket equals the length of the data packet in bytes; Overhead equals the length of protocol header overhead in bytes; #BurstPackets equals the number of modified data packets stored in the first logfile with the packet type value equal to the representation of “burst packet”; t1 equals a timestamp indicating when the first modified data packet is received in the client computer (1); t2 equals a timestamp indicating when the last modified data packet is received in the client computer (1); t3 equals the client-to-server-latency of the first modified data packet; t4 equals the client-to-server-latency of the last modified data packet.
 22. System according to claim 18, wherein the client computer (1) is arranged to read from the first logfile the round-trip-time and the sequence number, and the client computer (1) is arranged to calculate a roundtrip outage using: if(Rtt2−Rtt1)>t5 then roundtrip outage=true where Rtt2 equals the round-trip-time; Rtt1 equals the round-trip-time of the previous modified data packet, the client computer being arranged to identify the previous modified data packet by the sequence number; t5 equals a predefined amount of time.
 23. System according to claim 18, wherein the client computer (1) is arranged to read from the first logfile the client-to-server-latency and the sequence number, and the client computer is arranged to calculate a downlink outage using: if(Rtt4−Rtt3)>t5 then downlink outage=true where Rtt4 equals the client-to-server-latency; Rtt3 equals the client-to-server-latency of the previous modified data packet, the client computer being arranged to identify the previous modified data packet by the sequence number; t5 equals a predefined amount of time.
 24. System according to claim 19, wherein the client computer (1) is arranged to read from the first logfile the sequence number, and the client computer (1) is arranged to calculate an uplink outage using: if(Rtt6−Rtt5)>t5 then uplink outage=true where Rtt6 equals the server-to-client-latency; Rtt5 equals the server-to-client-latency of the previous modified data packet, the client computer being arranged to identify the previous modified data packet by the sequence number; t5 equals a predefined amount of time.
 25. System according to claim 22, wherein the client computer (1) is arranged to determine a number of lost packets between two modified data packets, by analyzing the sequence numbers.
 26. System according to claim 17, wherein the client computer (1) is arranged to combine the calculated values with low level measurement data from a mobile telephone and/or geographic information data.
 27. Method for measuring the quality of a data network (3) in a system comprising a client computer (1) and a server computer (2), the client computer (1) and the server computer (2) being arranged to communicate via the data network (3) using a connection-less transmission protocol, the method comprising the steps of sending one or more data packets (1001) from the client computer (1) to the server computer (2), the data packets comprising a first timestamp (103) indicating the time of sending, receiving at least one of the data packets in the server computer (2), sending, for each received data packet, a modified data packet (1002) from the server computer (2) to the client computer (1), the modified data packet comprising the first timestamp (103) and a second timestamp (105) indicating the time of receiving, sending one or more timeout data packets (1003) from the server computer (2) to the client computer (1) when a predefined amount of time lapsed (1004) since receiving the last data packet in the server computer (2).
 28. Method according to claim 27, the method further comprising the steps of reading from a server memory (2 b) in the server computer (2) a timeout value indicating the predefined amount of time, a server interval value and a quantity value, sending the timeout data packets (1003) with a server interval time equal to the server interval value, until a next data packet is received, and the maximum number of timeout data packets equals the quantity value.
 29. Method according to claim 28, the method further comprising the steps of reading from a client memory (1 b) in the client computer (1) for each data packet a client interval value, a client packet size value and a packet type value, sending the data packets (1001) with a client interval time equal to the client interval value, the data packets comprising the packet type value (101) and a client payload (104), the client payload (104) filling the data packets up to a first predefined size equal to the client packet size value. 